System and method for read-ahead enhancements

ABSTRACT

A method and system are provided for identifying type-ahead candidates. A method includes determining a context of past non-threaded emails of a user. The method further includes generating a context index associating the past non-threaded emails of the determined context with repeatable values within the past non-threaded emails. The method further includes receiving characters in a current email and determining a context of the current email. The method further includes determining matches between the current email and the past non-threaded in the context index. The method further includes identifying the corresponding repeatable values and matching the identified corresponding repeatable values with the received characters. The method further includes presenting the candidate words to the user for inclusion in the current email.

CROSS REFERENCE TO RELATED APPLICATION

The present application is a continuation of U.S. application Ser. No.11/029,756, filed Jan. 4, 2005, the contents of which are incorporatedby reference herein in their entirety.

FIELD OF THE INVENTION

The invention generally relates to a system and method for analyzingpossible repeatable values for placement into a data field and, moreparticularly, to a system and method for analyzing possible repeatablevalues based on user-defined criteria.

There are many applications today which have the ability to assist anend user with data entry. Applications such as Lotus Notes®, OutlookExpress®, That's Word®, and a host of others typically have some form oftype-ahead features which are intended to make the end user moreproductive or accomplish the related task more efficiency. A significantproblem with most existing solutions is that the repeatable data that ispresented to the user is not contextual. For example, some popular emailprogram assists a user with data entry in the “To” field by convenientlypre-filling the names of potential recipients by matching the charactersthe user has typed against the user's address book. In every case, thename that may be presented to the end user is the first match foundalphabetically. So, to expand on the previous example, if the user isattempting to type the name “Dave Johnson” and the user has four namesin the address book (namely Adams, Krantz, Jackson, and Johnson, forexample) than as the user types the characters “Day” the system suggestsvia type-ahead functionality “e Adams” as a most likely match. Thus, itbecomes obvious in this example that the last option presented to theuser is the one that the user wanted and would have been most helpfulhad it been the first option presented.

Some type-ahead systems improve type-ahead functionality by analyzingthe frequency of emails sent to and received by others and the historyof emails in the same thread. In these types of type-ahead systems themethod is limited to a correlation of threaded messages and the sendersand receivers of those messages, and does not attempt to make acorrelation between non-threaded messages. Threaded messages typicallyinclude those messages that are responses to responses or responses toan original message and are usually denoted by terms such as, forexample, “forwarded” or “reply to” and where the history of the previousrelated message is included in the most recent message. In other words,it may be characterized that the messages are directly “linked.” Thesesystems typically determine relationships between senders and receiverspurely on the threaded aspect and to no logical extension.

SUMMARY OF THE INVENTION

In an aspect of the invention, a method is provided for identifyingtype-ahead candidates. The method comprises the steps of matching one ormore characters in a non-threaded document with one or more receivedcharacters to identify one or more candidate words, selecting the one ormore candidate words based on the results of the matching step andpresenting and including the selected one or more candidate words into acurrent document.

In another aspect of the invention, a system for identifying type-aheadcandidates is provided. The system comprises at least one component toreceive one or more characters to provide a basis to determine a match,match one or more characters in a non-threaded document with thereceived one or more characters to identify one or more candidate wordsand select the one or more candidate words based on the results of thematch for presentation and inclusion into a current document.

In another aspect of the invention, a computer program product isprovided comprising a computer usable medium having readable programcode embodied in the medium. The computer program product includes atleast one component to receive one or more characters to provide a basisto determine a match, analyze at least one non-threaded document tomatch one or more characters in the non-threaded document with thereceived one or more characters to identify one or more candidate wordsand select the one or more candidate words based on the results of theanalyzing for presentation and inclusion into a current document.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing an illustrative environment of theinvention;

FIG. 2 is a flow diagram of an embodiment showing steps of using theinvention;

FIG. 3 is a flow diagram of an embodiment showing steps of using theinvention; and

FIG. 4 is a flow diagram of an embodiment of using the invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

This invention is directed, generally, to a system and method foranalyzing potential repeatable values for placement into a data fieldbased on user-defined criteria and/or contextual information fromcurrent or historical documents. The system and method includesanalyzing relationships between documents for the purpose of correlatingsender and receiver information into a context to more accuratelypopulate type-ahead functions in repeatable data fields. Threadedmessages are typically limited to those messages that are responses toresponses or responses to an original message and are usually denoted byterms such as, for example, “forwarded” or “reply to” and where thehistory of the previous related message is included in the most recentmessage.

The invention expands correlation into non-thread related documents toachieve a higher correlation rate. The expanded documents may be anyprevious email or associated documents of a sender or receiver,including any documents defined by user criteria. In the case ofstand-alone applications, such as word processors or spreadsheets, anyuser associated document, as defined by user criteria may be included ina contextual association for purposes of type-ahead analysis.

Careful application of logic and contextual information determines whichrepeatable data may be most meaningful to the end user. This data maycome from an analysis of the current document, stored data related tothe current document and a correlation between this and historical dataavailable on previous documents. The system and method of the invention,in embodiments, may also be used in conjunction with applications suchas web page fields (e.g., browsers), directory look-ups, instantmessaging (IM) clients and email clients to increase accuracy andtype-ahead hit rates. Documents that may be germane to a user contextmay be consulted for analysis. A context is typically arranged byfunction such as email related files (e.g., sent or received folders)and associated documents (e.g., attachments and linked documents), orarranged by folder structures on an application basis, such as wordprocessing files which may constitute a context for a word processingapplication.

A context may be formed as appropriate by essentially any type ofapplication employing type-ahead functionality by referencing files ordocuments as appropriate to the application. There may be common sharingof files and folders among differing applications such as, for example,address books, contact lists, or similar composite data.

FIG. 1 is a block diagram showing an illustrative environment of theinvention, generally denoted by reference numeral 100. The illustrativeenvironment includes one or more computers 105 (e.g., a personalcomputer) interconnected to a network 110 (e.g., the Internet, or localarea network (LAN)). Also included are one or more servers 115 that mayprovide one or more applications 125 such as email applications, wordprocessors, financial packages, or any other application utilizingtype-ahead functionality. The applications 125 may consult file storagesuch as database(s) 120 that may store current and/or historicaldocuments such as emails, IM messages, word processing documents, orother application data for analyzing context of a user's input, whichmay include a context index 455 (FIG. 4), as described below. Theillustrative environment 100 is but one example and one of ordinaryskill in the art would recognize that many other variations may existincluding non-server arrangements, all of which are contemplated by theinvention.

By way of example, an email system is used to illustrate the system andmethod of the invention, but may be applied to other applicationsemploying some type of correspondence and/or associated documents thatmay comprise a context. For example, a program agent, which may be anapplication 125, may analyze past emails, if available, or keep arunning log/data base of messages sent, a record to whom, and messagesreceived and from whom. A table may be created of corresponding valuesfor emails that are considered similar in subject matter. This table mayconsist of uncommon words that show up in multiple emails and alsocommon subject matter that may not necessarily have the same uncommonwords. This correlation table may be derived by a combination of (i)pre-set lists of known uncommonly used words and/or (ii) a real-timeanalysis of the collection of emails and the related frequency of wordswhereby the least used, 10%, for example, of the words become thetargets for comparison.

The program agent 125 may then correlate words and phases within acurrent email or associated documents (such as attachments or linkeddocuments) to similar words and phases in past emails (and attachmentsor linked documents), which may not be in the same current thread, togive people or entities who were part of those previous correspondences(i.e., those who where senders or recipients) a heavier weight aschoices for the type-ahead function in the current email. For example,the words “Disney,” “Daffy,” and “Mickey” may be in the main body of thecurrent email and the program agent 125 may find a past email, e.g., notin the same thread, sent several months ago with the same three words inwhich the user sent an email to Eric Smith, The program agent 125 maydetermine that these words constitute a unique variation and highcorrelation, and then as the user types the letters “Eric” in the “SendTo” field, the program agent then prefills “Eric Smith” instead of anyother Eric that may be in the address book.

FIG. 2 is a flow diagram of an embodiment showing steps of theinvention, starting at step 200. FIGS. 2-4 may equally represent ahigh-level block diagram of components of the invention implementing thesteps thereof. The steps of FIGS. 2-4 may be implemented on computerprogram code in combination with the appropriate hardware. This computerprogram code may be stored on storage media such as a diskette, harddisk, CD-ROM, DVD-ROM or tape, as well as a memory storage device orcollection of memory storage devices such as read-only memory (ROM) orrandom access memory (RAM). Additionally, the computer program code canbe transferred to a workstation over the Internet or some other type ofnetwork.

At step 205, documents and/or files that may be deemed germane to theuser's context are identified for inclusion for analysis andcross-checking with user input to determine any type-ahead candidates.At step 210, a check may be made to determine if the user is replying toa communication such as an email, an IM, or the like. If not, theprocessing continues with step 245. However, if the user is replying toa communication, then at step 215, a list may be created from availablecontext information (e.g., past emails or IMs) that reflects any usersthat have been contacted in the past. The list may be ordered based onfrequency (e.g. descending order based on frequency). At step 220, asub-ordering may be applied to reflect those contacts that have beenmost recently contacted (e.g., in descending order), which may beanother list.

At step 225, a check may be made to determine if the user is respondingto a previous communication. If not, the processing continues at step240. Otherwise, at step 230, a list may be created that reflects knowncontacts that were included in previous communications with the user.The contacts may have been included in any one of the “To”, “cc:”,“bcc:” fields, for example. At step 235, any name or contact identifiedin the body of the previous or current correspondence and/or attachmentsmay be compiled to generate candidates for type-ahead selection.

At step 240, a list may be created based on the existing names in the“To:” field reflecting the most often addressed (e.g., emailed) contactsthat were also a part of other emails associated with the names in the“To:” field. That is, any contacts that were included in past emails ofany of the current “To:” addresses may become candidates for atype-ahead auto-populate action. At step 245, any contacts orwords/phrases identified by a user preference as a priority may beincluded as candidates or given higher preference, particularly ifalready a candidate on a previously compiled list.

At step 250, candidate words and/or phrase may be identified based onthe current document or message body to past documents or message bodieshaving the same words and/or phrases. At step 255, based on thecandidates created, one or more candidate type-ahead proposals may beselected for auto-populating. The selection process may give precedenceto any list that the user may have given a higher weight. A user mayestablish a preference profile and, if applied, will allow a user toassign more weight to the available data being evaluated. Inembodiments, the system and method of the invention may promotecandidate choices to higher levels, in accordance with user preferences.The process ends at step 260.

FIG. 3 is a flow diagram of an embodiment showing steps of using theinvention, starting at step 300. At step 305, input may be monitored forcharacter input. At step 310, character input may be recognized asreceived. At step 315, the character input may be compared to availablematches from a user's context (e.g., files, folders and/or messages,both current and historical/stored) associated with the application(e.g., email, IM, word processing, or the like) This may be partial orfull matches on words, phrases, contacts or names, for example, ascharacter input permits.

At step 320, a check is made whether a preference profile exists for theuser. If so, at step 325, user preferences are applied with anappropriate specified weight. These preferences may include preferredcontacts or names, words and/or phrases. If, however, a preferenceprofile does not exist, then processing continues with step 330. At step330, any predefined weights for contextual matches are assigned tocandidate words, phrases or contacts. At step 335, weights for frequencyof occurrence matches may be assigned to candidate words, phrases orcontacts. That is, a weight may be assigned based on the frequency ofoccurrence of a word, phrase or contact found within context sources.

At step 340, weights may be assigned to candidate words, phrases orcontacts for time-based proximity matches. That is, for example, matchesthat occur using more recent sources (i.e., documents or communications)within a predetermined number of days defined as “recent,” may havehigher weighting. Likewise, matches using older sources may have lowerweighting assigned. At step 345, weights may be assigned for inclusivereferences as derived from data within the current message or entity(e.g., current email, IM, short message service (SMS) message, addressbook entry, or the like). Inclusive references include these textualmatches found within a current message.

At step 350, weights may be assigned based on matches in associativereferences. Associative references are typically derived from dataoutside the current message or entity, and may be indirectly locatedthrough entities referencing other entities which have matching topics(e.g., subject line), words or phrases, contacts, or the like. At step355, one or more choices with “heaviest” weights may be presented to theuser for type-ahead choices. The presentation may include the top “N”heaviest weighted choices, or simply the heaviest weighted choice. Atstep 360, a check is made whether the user has accepted a profferedtype-ahead choice. If not accepted, then processing continues with step310 to receive more character input. If, however, the user accepts aproffered type-ahead choice, then at step 370, the accepted choice maybe made permanent. At step 375, the process ends.

In this manner, a user may be offered one or more type-ahead choicesthat have been analyzed in view of a user's context which may include,for example, email history, document association, user preferences,document(s) word occurrences, time-based association, or the like. Thistypically provides a user with better probabilities that the profferedtype-ahead offerings may be more accurate, thus enhancing productivity,user satisfaction and accuracy.

FIG. 4 is a flow diagram of an embodiment of using the invention,starting at step 400, and another flow may start at step 428, asexplained below. At step 405, a user may input characters into a datafield (e.g., an email, IM, or document). At step 410, the characterinput is compared to potential matches with type-ahead candidate words,phrases or contacts. At step 415, a check is made whether additionalcharacter input is required to complete a potential match (which may bea partial match of a word). If additional characters are required, thenprocessing continues at step 410 to await more character input. If,however, additional character input is not necessary, then at step 420,the current document may be analyzed for context such as keywords andphrases. Processing continues with step 460, however, a second flowwhich may provide input to step 460 is now described.

A second parallel flow may start at step 428 and this flow may precede,be concurrent, or asynchronous with the flow entered at step 400.Typically, the flow entered at step 428 may be executed by one or moreseparate agents that scans for changes or new documents entering thesystem for updating a context index (e.g., a database) for use by theflow entered at step 400. Steps 428 through 450, in embodiments, mayoccur in parallel or asynchronous with steps 400 through 470. At step430, a next (or first, as appropriate) stored document associated withthe user's context may be identified. This may include historical emailsand/or attachments, messages, or documents associated with the user andappropriate for the user's application (e.g., word processing or thelike). At step 435, the next stored document may be analyzed for contextsuch as words, phrases, contacts, or the like.

At step 440, any addressable names or contacts may be associated withthe document currently being analyzed. Names and associated weights maybe mapped to a specific document for storing in the context index 455.The weights assigned may denote a frequency of how often each nameoccurred. A composite weight may be included for each name for allrelated documents scanned. This may include mining contact names fromthe “from:” field, “to:” field, “Cc:” field and “Bcc:” field. At step445, any results from the analysis of the next document are indexed andthe results may be added (or updated) to a context index 455 fordefining all currently known candidates in the current context(s) andfor use in prioritizing matches (e.g., step 460) for type-aheadcandidates for any user input. Processing continues at step 450 whichchecks for any remaining documents. If any additional documents, theprocessing continues at step 430, otherwise the parallel flow ends atstep 475. At a predetermined interval, step 428 may again be entered.

At step 460, matches from the current document and/or from the contextindex may be prioritized. In embodiments, the matches may also receiveweighting as determined by the user's preferences, time-association(e.g., more recent documents provide a higher weight), or the like tofacilitate the prioritization. At step 465, the higher prioritizedcandidates (or, alternatively, the highest prioritized candidate) may bedisplayed in results field for type-ahead selection by the user.

In embodiments, a client or server process may examine every new message(e.g., email message) and collect the unique addresses from the addressfields (e.g., “from:”, “to:”, “Cc:”, “Bcc:”) and store them in a memoryor database. The process may then compare these addresses to see if theyare already stored in the user's address book. If the addresses are notalready stored in the address book, then the process may compare theseaddresses to see if they are stored in a “virtual address book”maintained by the system. The virtual address book automaticallymaintains addresses so that the user does not have to specifically addaddresses to the virtual address book. If any of the newly foundaddresses are not in this virtual address book, then the system adds anynew addresses to the virtual address book. This may include creating anew record and populating the record with a “user name” parsed from SMTPOriginator field, “From:” field, “Reply to” field, and the “address” maybe populated from the email portion of the SMTP “Originator field,”“From field,” in “reply to” fields. The current date/time may be used topopulate the “recently received” field with an initial value of “1”inserted into the “frequency received” field and if the message is partof a conversation thread, a thread id is used to populate the “sharedthread with” field with a value of 1 [O=false, 1=true], for example. Forany existing addresses that match the newly found addresses, theirvirtual address book records may be updated by posting the currentdate/time in a “recently received” field of the virtual address bookentry, and by incrementing the value in the “frequency, received” fieldby 1.

The system may also perform a similar process on new outgoing messages.For example, looking for any addresses, creating new records with username, email address, recently sent (i.e., time/date) and frequency sent(e.g., initial value 1). Also, updating any existing records fields forrecently sent to (time/date) and frequency sent (increment existingvalue by 1), and then if the message is part of a conversation threadthe system may populate the “shared thread with” field with a value of 1[O=false, 1=true], as well as the “participated in a thread with” fieldwith a value of 1 [O=false, 1=true]. The page contains user interfacethat permits the user to edit the list—manually adding, removing ormodifying any of the fields in the address record, as well as to selectany number of addresses (e.g., using conventional gestures foraccumulating selections in a list) that are subsequently used in theaddressing of new or existing outgoing messages. The system may alsoprovide a user interface comprising a page for displaying the list ofaddresses or names from the virtual address book.

This list may contain filters that show only name and addresses of thosemessages that match choices of:

-   -   “recently received” (with number of days that are considered        recent, showing only those addresses with date values in the        recently received field within the date range from today back        the number of days indicated),    -   “recently sent to” (with number of days that are considered        recent, showing only those addresses with date values in the        recently sent to field within the date range from today back the        number of days indicated),    -   “frequently received from” (with a number representing the        cutoff value for frequency, showing only those exceeding that        value),    -   “frequently sent to” (with number representing the cutoff value        for frequency, showing only those addresses exceeding that        value),    -   “shared thread with” (showing only those addresses with a true        value in the shared thread field),    -   “participated in thread with” (showing only those addresses with        a true value in the participated in thread with thread field).

This page may also provide a second ordered list containing a singleitem matching each label of the above fields and user interface forreordering this list. The purpose of this list is in determining the“priority” when the addressing auto-completion process matches to morethan one address in the virtual address book. The user may order thefields so that certain fields are considered more important in matchingduring auto-completion.

In embodiments, this may also allow the addressing of messages throughauto-completion of names based on the records and their values from thevirtual address book. The process may auto-complete to the name thatmatches the characters the user has typed, and in the event there aremore than one address that matches the characters typed, theauto-complete system uses the ordered list of virtual address bookfields (described above) to determine which of the multiplicity ofaddresses to show the user first. The auto-complete system may alsoprovide a user interface (e.g., a graphical user interface) that permitsthe user to cycle through the addresses (e.g., using arrow keys).

Also, the entire virtual address book may be kept and maintained on theclient machine. This provides for the above functionality when theclient is not able to communicate with a server that traditionallymaintains address books and auto-complete functionality.

While the invention has been described in terms of embodiments, thoseskilled in the art will recognize that the invention can be practicedwith modifications and in the spirit and scope of the appended claims.

1. A method of identifying type-ahead candidates, comprising:determining a context of a plurality of past non-threaded emails ordocuments of a user by analyzing the plurality of past non-threadedemails or documents for words or phrases, wherein the plurality of pastnon-threaded emails or documents are associated with a softwareapplication; generating a context index associating the plurality of thepast non-threaded emails or documents of the determined context withcorresponding repeatable values within the plurality of pastnon-threaded emails or documents; receiving one or more characters in acurrent email or document of the software application; determining acontext of the current email or document by analyzing the current emailor document for words or phrases in the current email or document,wherein the context of the current email or document corresponds to thecontext of past non-threaded emails or documents; determining matchesbetween the current words or phrases and words or phrases of theplurality of documents of the context index; identifying, based on thedetermined matches, one or more of the corresponding repeatable values;matching the identified corresponding repeatable values with the one ormore received characters to identify one or more candidate words; andpresenting the one or more candidate words to a user on a computer astype-ahead choices for inclusion in the current email or document. 2.The method of claim 1, wherein: the repeatable values are addressablenames or contacts; and the context index associates the addressablenames or contacts with weights based on their frequency of occurrencewithin the plurality of past non-threaded emails or documents.
 3. Themethod of claim 1, further comprising: creating a preferences profilethat defines preferred words or phrases for use in prioritizing the oneor more candidate words; and prioritizing the one or more candidatewords based on the preferences profile.
 4. The method of claim 1,wherein analyzing the current email or document comprises: analyzing thepast non-threaded emails or documents for their context by identifyingmatching keywords or phrases between the past non-threaded emails ordocuments and the current email or document; associating thecorresponding repeatable values for the matched past non-threaded emailsor documents with the identified matching keywords or phrases; andcreating the context index of the corresponding repeatable values foruse by the determining matches step.
 5. The method of claim 1, furthercomprising prioritizing the one or more candidate words based on thecontext index.
 6. The method of claim 1, further comprising receiving atleast one additional character when more than one match occurs andrepeating the matching step.
 7. The method of claim 1, furthercomprising making one of the one or more candidate words a permanentword in the current email or document.
 8. The method of claim 1, whereinthe current email or document is in response to or related to one ormore previous communications, and further comprising the steps of:creating a list of contacts from the one or more previouscommunications; creating a list of any contacts in a body of the one ormore previous communications; and creating a list of contacts includedin any past non-threaded emails or documents involving any contactsassociated in any address field in any of the one or more previouscommunications.
 9. The method of claim 8, wherein the presenting step isbased on any of the lists.
 10. The method of claim 1, wherein theanalyzing the past non-threaded emails or documents comprises: creatinga database, which is a running log of messages sent, a record of to whomthe messages were sent, messages received, and a record of from whom themessages were received, the database comprising a correlation tablecomprising: corresponding values for the messages sent and the messagesreceived that are considered similar in subject matter; and one or moreuncommon words that appear within the messages sent and the messagesreceived; wherein the corresponding repeatable values for the messagessent and the messages received are the corresponding values in thecontext index.
 11. The method of claim 10, wherein the database isderived by a combination of (i) pre-set list of the one or more uncommonwords that are known and (ii) a real-time analysis of the messages and arelated frequency of words in the messages in which a thresholdpercentage of usage defines targets for comparison.
 12. The method ofclaim 11, further comprising displaying a list of addresses and namesfrom a virtual address book, the list including one or more filters thatshow only the addresses and the names that are received, sent to,received from, shared thread with, or participated in thread with.
 13. Asystem for identifying type-ahead candidates, comprising at least onecomponent to: analyze a plurality of past non-threaded emails ordocuments of a user for words or phrases, wherein the plurality of pastnon-threaded emails or documents are associated with a softwareapplication; generate a context associating a plurality of the pastnon-threaded emails or documents of the determined context of pastnon-threaded emails or documents with corresponding repeatable valuesidentified within the plurality of past non-threaded emails ordocuments; receive in a current email or document of the application oneor more characters to provide a basis to determine a match; analyze thecurrent email or document for current words or phrases; determinecorrelations between the current words or phrases within the currentemail or document and similar words or phrases in the database;identify, based on the determined correlations, one or more of thecorresponding repeatable values identified within the past non-threadedemails or documents; match the corresponding repeatable values with thereceived one or more characters to identify one or more candidate words;prioritize the one or more candidate words; present the one or morecandidate words to a user on a computer as type-ahead choices; andselect the one or more candidate words based on the results of the matchfor presentation and inclusion into the current email or document,wherein the at least one component comprises: hardware for implementingcomputer program code, a storage medium, and a program agent.
 14. Thesystem of claim 13, further comprising the at least one component toassign a weight to the one or more candidate words based on the matchwith the corresponding repeatable values, a frequency match, a timebased proximity, an inclusive reference, and an associative match. 15.The system of claim 13, wherein the at least one component selects theone or more candidate words based at least in part on an assignedweight.
 16. The system of claim 13, wherein analyzing the current emailor document comprises: analyze the past non-threaded emails or documentsfor their context by identifying matching keywords or phrases betweenthe past non-threaded emails or documents and the current email ordocument; associate corresponding values for the matched pastnon-threaded emails or documents with the identified matching keywordsor phrases; and create the context index of the corresponding repeatablevalues for use by the correlating step, wherein the correspondingrepeatable values are contacts listed as senders or receivers of thematched past non-threaded emails or documents.
 17. The system of claim13, further comprising the at least one component to prioritize the oneor more candidate words based at least in part on the context index. 18.The system of claim 13, further comprising the at least one componentto: receive at least one additional character when more than one matchoccurs; and make one of the one or more candidate words a permanent wordin the current email or document.
 19. A computer program productcomprising a computer usable storage medium having program code storedin the storage medium, the computer program product includes at leastone component operable to: determine a context of a plurality of pastnon-threaded emails or documents of a user by analyzing the plurality ofpast non-threaded emails or documents for words or phrases, wherein theplurality of past non-threaded emails or documents are associated with atype of software application; generate a context index associating theplurality of the past non-threaded emails or documents of the determinedcontext with corresponding repeatable values within the plurality ofpast non-threaded emails or documents; receive one or more characters ina current email or document of a software application belonging to thetype of software application; determine a context of the current emailor document by analyzing the current email or document for words orphrases in the current email or document, wherein the context of thecurrent email or document corresponds to the context of pastnon-threaded emails or documents; determine matches between the currentwords or phrases and words or phrases of the plurality of documents ofthe context index; identify, based on the determined matches, one ormore of the corresponding repeatable values; match the identifiedcorresponding repeatable values with the one or more received charactersto identify one or more candidate words; and present the one or morecandidate words to a user on a computer as type-ahead choices forinclusion in the current email or document.